System and method for transmitting dynamic content to mobile devices

ABSTRACT

A method of transmitting dynamic content to a mobile device includes: storing content in a memory of a kiosk deployed in a facility; receiving, via an input device of the kiosk, a command to present the a portion of the content; responsive to receiving the command: controlling an output device of the kiosk to present the portion of the content; and transmitting, to a routing server via a network, a preconfigured identifier of the kiosk and an identifier of the portion of the content, for subsequent retrieval by a mobile computing device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/123,564, filed Sep. 6, 2019, which claims priority from U.S.provisional patent application No. 62/556,769, filed Sep. 11, 2017. Thecontents of the above-mentioned documents are incorporated herein byreference.

FIELD

The specification relates generally to communications with mobiledevices, and specifically to a system and method for transmittingdynamic content to mobile devices.

BACKGROUND

Fixed kiosks are often deployed in facilities to provide mappinginformation and directions to patrons of the facilities. As the kiosksare fixed, however, such mapping information may only be viewed at thekiosks themselves, and becomes inaccessible when the patron moves awayfrom the kiosk to travel toward a destination presented on the kiosk.The patrons frequently carry mobile computing devices, and some systemspermit such devices to obtain mapping information independently from thekiosks. However, such systems typically require additional software tobe installed on the mobile devices (e.g. distinct applicationscorresponding to each facility), increasing the complexity of thesystems, and imposing computational load and network usage on the mobiledevices.

BRIEF DESCRIPTIONS OF THE DRAWINGS

Embodiments are described with reference to the following figures, inwhich:

FIG. 1 depicts a system for dynamically transmitting content to mobiledevices;

FIG. 2 depicts a method of dynamically transmitting content to mobiledevices;

FIGS. 3A and 3B depict example data displayed by the kiosk and mobiledevice of FIG. 1 during the performance of the method of FIG. 2; and

FIG. 4 depicts a system for dynamically transmitting content to mobiledevices, according to another embodiment.

DETAILED DESCRIPTION

FIG. 1 depicts a system 100 for dynamically transmitting content tomobile devices. In the examples discussed below, the content transmittedto the mobile device(s) is mapping information (e.g., portions of afacility map surrounding one or more selected locations). In otherexamples, however, the content can include any one or more of theabove-mentioned mapping information, scheduling information (e.g. hoursof operation of a facility), event information (e.g. locations, datesand times of events), and the like.

The system 100 includes a kiosk 104 deployed at a fixed location withina facility, such as a hospital, a shopping mall, or the like. Aplurality of kiosks may be deployed at distinct fixed locations withinthe facility, each of which may operate as described below in connectionwith the kiosk 104. The kiosk 104 includes a non-transitorycomputer-readable storage medium in the form of a memory 108 (e.g. oneor more integrated circuits including any suitable combination ofvolatile and non-volatile memory) storing content in a repository 109,which in the present example is mapping information corresponding to thefacility (e.g. a graphical map of the facility). The kiosk 104 alsoincludes an output device for presenting portions of the mappinginformation, and an input device for receiving commands indicating whichportions of the mapping information to present. In the present example,the input and output devices are implemented as a display with anintegrated touch screen 112. In other embodiments, the kiosk 104 can beprovided with separate input and output devices (e.g. a display and adistinct touch pad). Various other input and output devices are alsocontemplated, including microphones, speakers and the like.

The kiosk further includes a cant roller 116, such as a centralprocessing unit (also referred to simply as a processor), anapplication-specific integrated circuit (ASIC) or the like. Viaexecution of computer-readable instructions stored in the memory 108,such as a control application 110, the controller 116 is configured toreceive commands via the touch screen, select portions of the mappinginformation from the memory 108 (i.e. from the repository 109) andpresent the selected portions on the display 112. The controller 116 canalso be configured to generate path information illustrating directionsbetween a location of the kiosk 104 (e.g., preconfigured in the memory108 with respect to the above-mentioned facility map) and a location onthe map selected via the above-mentioned input commands. The pathinformation can also be presented on the display 112, for example as anoverlay on the mapping information.

The kiosk 104 also includes a communications interface 120, such as anEthernet controller, wireless radio assembly, or the like, forcommunicating with other computing devices over a network 124 (e.g. anyone of, or any suitable combination of, local area networks and widearea networks, including the Internet). In particular, the kiosk 104 isconfigured to communicate with a routing server 128 of the system 100,as will be discussed below in greater detail. The kiosk 104 may also beconfigured to communicate, via the network 124, with a content server132 hosting a master content repository 134. For example, the contentserver 132 can be configured to periodically provide content updates tothe kiosk 104 (e.g. updates to be applied to the repository 109,reflecting changes to the mapping information defined in the repository109).

The routing server 128 includes a controller 136, such as a centralprocessing unit (also referred to simply as a processor), anapplication-specific integrated circuit (ASIC) or the like. Thecontroller 136 is coupled to communications interface 138 enabling therouting server 128 to communicate with other computing devices via thenetwork 124. Via execution of computer-readable instructions such as arouting application 140 stored in a memory 142 coupled to the controller136, the controller 136 is configured to receive data from the kiosk 104responsive to user interaction with the kiosk 104 (as will be discussedbelow), and to store the data in a routing repository 144 for subsequentretrieval and provision to a mobile device 150, as will be discussedbelow. Although the routing server 128 and the content server 132 areshown as distinct physical components of the system 100, in otherembodiments the functionality of the routing server 128 and the contentserver 132, as discussed above, may be implemented on common hardware(e.g. on one physical server or associated set of servers).

The system 100 also includes the above-mentioned mobile device 150, suchas a smartphone, tablet computer, or the like, typically operated by apatron of the above-mentioned facility. The mobile device 150 includes acommunications interface enabling the mobile device 150 to communicatewith other computing devices (e.g. the routing server 128) via thenetwork 124. The communications interface of the mobile device 150 canalso enable to the device 150 to communicate locally with othercomputing devices, such as the kiosk 104 or a component physicallysupported by the kiosk 104 (though not necessarily communicativelyconnected to the controller 116). The communications interface of themobile device 150, in other words, can include any suitable combinationof radios, network controllers and the like, to enable local and/orwide-area communications. The mobile device 150 also includes acontroller (e.g. a processor, ASIC or the like) interconnected with amemory for storing and executing one or more applications, such as a webbrowser application. The mobile device 150 also includes input andoutput devices, for example in the form of a touch screen integratedwith a display. As will be discussed in greater detail below, the mobiledevice 150 also includes a data capture module configured to captureidentifying data from the kiosk 104. The data capture module can take avariety of forms, corresponding to the various mechanisms by which thekiosk 104 can make the identifying data available. Example data capturemodules include a camera, the above-mentioned communications interface(e.g. a Bluetooth or other short-range radio component of thecommunications interface), and the like.

In general, the kiosk 104, the routing server 128 and the mobile device150 interact to enable the selection of portions of mapping informationat the kiosk (e.g. by manipulation of the display/touch screen 112 by anoperator of the mobile device 150), and the transmission of thoseportions of the mapping information to the mobile device 150. To thatend, as noted above, the content server 132 stores a copy of the mappinginformation in the master repository 134, and as will be seen below,transmits portions of the mapping information to the mobile device 150in response to requests from the mobile device 150.

Turning to FIG. 2, a method 200 of dynamically transmitting content tomobile devices (such as the mobile device 150) is illustrated; themethod will be described below in conjunction with its performance onthe system 100. At block 205, the kiosk 104 is configured to receiveinput from an operator of the mobile device 150 via the display/touchscreen 112, and to present content from the repository 109 on thedisplay/touch screen 112, such as a portion of a map of the facility inwhich the kiosk is deployed and a path from the location of the kiosk104 to a destination selected by the operator. That is, the inputreceived at block 205 can include a search request for a particulardestination (e.g. a store, department or the like), and presentation ofthe content from the repository 109 can include retrieving thepreconfigured location of the kiosk 104 itself and computing a path fromthe preconfigured location to the destination. The path generationmentioned above can be performed according to any of a variety ofsuitable path generation operations, examples of which will readilyoccur to those skilled in the art. Turning to FIG. 3A, the kiosk 104 isshown having presented a portion 300 of a map on the display 112, alongwith a path 304 generated by the controller 116 between a preconfiguredkiosk location 305 (i.e. a start point of the path 304) and adestination 306 selected by the operator of the mobile device 150. Aname 307 of the destination (e.g. the podiatry department of ahealthcare facility such as a hospital) may be presented with the map300.

Returning to FIG. 2, at block 210, the kiosk 104 is configured totransmit to the routing server 128, via the network 124, an identifierof the kiosk 104 (e.g., uniquely identifying the kiosk 104 among otherkiosks in the same facility, or among kiosks at a plurality offacilities) and a content identifier. The kiosk identifier ispreconfigured and stored in the memory 108, for example as a string(e.g., “K104”). The content identifier serves to identify the portion ofthe map 300 presented at block 205, and the path 304 shown on thedisplay 112. The content identifier may, for example, be a locationidentifier (in a frame of reference established in the mappinginformation stored by the kiosk 104, for example), or a pair of locationidentifiers referring to a starting point (typically the preconfiguredlocation 305 of the kiosk 104) and the endpoint of the path 304 (thatis, the selected destination 306 referred to above). Thus, in thepresent example, the kiosk 104 transmits the kiosk identifier “K104” anda content identifier in the form of the location identifiers “from=A3”(corresponding to the kiosk location 305) and “to=V5” (corresponding tothe destination 306) at block 210. More specifically, in the presentexample, the content identifier is transmitted at block 210 in the formof a URL containing the above location identifiers (e.g.,“m.abc.ca/from=A3&to=V5”). As will be discussed below, the URL alsoidentifies the content server 132 as the source of the content.

At block 215, the server 128 is configured to receive the contentidentifier and the kiosk identifier sent at block 210. Thus, the routingserver 128, in the present example, receives a message from the kiosk104, the body of which contains the above-mentioned URL. The server 128is further configured to store a link in the routing repository 144,between the content identifier and the kiosk identifier, thus indicatingwhat content the kiosk 104 is currently displaying (i.e. presenting onthe touch screen/display 112). As will now be apparent, the routingserver 128 can store a plurality of such links for a respectiveplurality of kiosks 104, either within the same facility or distributedacross multiple facilities. The link can be stored with a timestampindicating the date and/or time of receipt of the content and kioskidentifiers. The link includes both the kiosk identifier and the contentidentifier. Continuing with the above example in which the kiosk 104transmits the URL “m.abc.ca/from=A3&to=V5” to the routing server 128,along with its own identifier “K104”, the routing server 128 can beconfigured to add a record to the repository 144 including a first fieldcontaining the kiosk identifier K104, a second field containing theabove URL (i.e. the content identifier), and a third field containingthe date and time of receipt of the kiosk and content identifiers.

At block 220, the mobile device 150 is configured to obtain a serveridentifier and a kiosk identifier. The kiosk and server identifiers aretypically obtained from the kiosk 104, but need not be activelytransmitted by the kiosk 104; the transition from block 215 to block 220is therefore shown in dashed lines. For example, the identifiers may beencoded in a machine-readable indicium (e.g. a QR code) presented on thedisplay 112, printed on a housing of the kiosk 104, or the like. In suchexamples, the mobile device 150 is configured to obtain the identifiersby capturing an image of the indicium ad decoding the identifiers fromthe image. In other examples, as shown in FIG. 3A, the kiosk 104includes a local communications interface 308 (e.g. integrated with theinterface 120, or implemented as a discrete component of the kiosk 104)such as a near-field communication (NFC) tag or other radio frequencyidentification (RFID)-based tag, a Bluetooth low energy (BLE) beacon, orthe like. The local communications interface 308 stores the kiosk andserver identifiers, and is configured to transmit the identifiers to themobile device 150 according to any suitable short-range communicationsprotocol. The mobile device 150 therefore includes a complementaryinterface, as noted earlier in connection with FIG. 1, and is configuredto obtain the identifiers via any suitable sequence of communicationswith the interface 308, dependent on the technology employed toimplement the interface 308. In some examples, the local communicationsinterface 308 is implemented as a BLE interface, and the kiosk andserver identifiers are provided to the mobile device 104 according tothe Eddystone protocol.

Of particular note, the server and kiosk identifiers can be stored orotherwise presented on or by the kiosk 104 in a substantially fixedmanner. That is, the identifiers need not be updated over time,irrespective of which mobile device 150 obtains the identifiers, andirrespective of what content is presented on the display 112 when themobile device 150 obtains the identifiers. Through the mechanismsdiscussed herein, the mobile device 150 is nevertheless provided withdynamic content from the repository 144.

The kiosk identifier obtained at block 220 is the same identifier asthat sent to the routing server 128 by the kiosk 104 at block 210 (i.e.,“K104” in the present example). The server identifier identifies anetwork address of the routing server 128 (e.g. a URL for the routingserver 128). At block 225, the mobile device 150 is configured to send arequest to the server 128 employing the above-mentioned URL.Specifically, in the present example, the identifiers obtained at block220 are obtained as a single string, such as a URL identifying therouting server 128 and including the kiosk identifier as an argument. Anexample string 312 is shown in FIG. 3A, including the routing serveridentifier “m.xyz.ca” and the kiosk identifier “K104”. Specifically, inthe present example the routing server identifier and the kioskidentifier are transmitted to the mobile device 150 as a URL (e.g.formatted according to the Eddystone protocol, as noted above).

At block 230, the routing server 128 is configured to receive therequest from the mobile device 150 and retrieve the content identifier(which is not included in the request sent at block 225) previouslystored in the repository 144 in association with the kiosk identifier atblock 215. That is, the routing server 128 is configured to retrieve thecontent identifier from the repository 144 using the kiosk identifierreceived at block 230 to look up the corresponding link (stored at block215) containing the content identifier. Having retrieved the contentidentifier (the above-mentioned URL “m.abc.ca/from=A3&to=V5” in thepresent example), the routing server 128 is configured to provide thecontent identifier to the mobile device 150 at block 235. The provisionof the content identifier at block 235 serves to redirect the mobiledevice 150 to the content server 132, as the content identifier containsthe domain “m.abc.ca”, which identifies the content server 132.

At block 240, the mobile device 150 is configured to receive theredirect URL mentioned above (i.e., the content identifier,“m.abc.ca/from=A3&to=V5”) and send a further request to the contentserver 132 according to the redirect URL. The content server 132, inturn, is configured to receive the request at block 245, and to retrieveand send the relevant portion of the mapping information from therepository 134 (which, as noted earlier, contains a master copy of themap content in the repository 109 of the kiosk 104). In particular, thecontent redirect string provided to the mobile device 150 and requestedfrom the content server 132 serves to identify a portion of the map asstored at the content server 132, for example bounded by a startlocation (e.g., the kiosk location) and the selected endpoint location,for retrieval and transmission to the mobile device 150. As seen in FIG.3B, the content 320 received and presented by the mobile device 150 atblock 250 includes a similar (and in some examples, identical) portionof the map as displayed by the kiosk 104. As also seen in FIG. 3B, theURL 324 received at block 240 includes an identifier of the contentserver 132 (“m.abc.ca”) as well as the location identifiers mentionedearlier. The content 320 returned to the mobile device 150 by thecontent server 132 at block 245 includes, in addition to the relevantportion of the map, the path 304. The path 304 need not be explicitlyidentified in the data exchanged by the routing server 128, kiosk 104,and mobile device 150 prior to block 240. Rather, the content server 132can be configured to execute the same path generation operation asimplemented by the kiosk 104, ensuring that for a given start anddestination locations, the content server 132 and the kiosk 104 generatethe same path 304.

Returning to FIG. 2, at block 255, the routing server 128 is configuredto purge (i.e., delete from memory) the link stored at block 215. Thelink may be purged in response to various conditions being met. Forexample, the server 128 can be configured to purge each link stored atblock 215 after a configurable time period (e.g. two minutes). In otherexamples, the server 128 can be configured to purge the link after arequest is received from a mobile device 150 at block 230. In stillfurther examples,

As will be apparent, in some situations the link stored at block 215 maybe purged at block 255 before the mobile device 250 has sent the requestat block 225 (e.g. if there is a delay in obtaining the identifiers bythe mobile device 250). The routing server 128 may be configured toreturn an error message to the mobile device 250 at block 235, ratherthan the redirect.

Variations to the above systems and methods are contemplated. Forexample, the routing server 128 and the content server 132 can becombined, such that the redirect at block 235 is omitted. In furthervariations, to protect the privacy of the mobile device 150, in additionto the above mechanisms for purging the link stored at block 215 thekiosk 104 and the routing server 128 can be configured to deployauthentication tokens. For example, the kiosk 104 can present on thedisplay 112 a token for inclusion in the request at block 225. Forexample, the token may be entered via an input device on the mobiledevice 150, and sent along with the kiosk and server identifiersobtained at block 220. The kiosk 104 may be configured to cycle througha plurality of tokens (e.g. at random, with a seed also stored at theserver 128). Thus, a subsequent mobile device may be prevented fromretrieving the same content shown in FIG. 3B because the token is nolonger presented on the display 112.

In further embodiments, at block 245 the content server 132 isconfigured not only to transmit content to the mobile device 150 asdiscussed above, but also to establish a persistent bidirectionalconnection with the mobile device 150 (e.g. via the WebSocket protocolor any other suitable communications protocol). For example, the contentserver 132 and the mobile device 150 can exchange socket identifiers(e.g. each consisting of an IP address and a port number, or any othersuitable set of parameters) and store the socket identifiers in memory.The content server 132 is then configured to transmit the content to themobile device 150 over the above-noted persistent connection. Further,the content server 132 can be configured to retrieve and transmitfurther content to the mobile device 150, with or without furtherrequests from the mobile device 150. The further content can includeupdated map data, e.g. illustrating a different portion of the facilityor containing a different path (e.g. responsive to receiving anindication of a current location of the mobile device 150 at the contentserver 132 via the persistent connection). The persistent connection istorn down responsive to an indication from the mobile device 150 thatthe browser application at the mobile device 150 has been terminated.

In further embodiments, as shown in FIG. 4, the system 100 can includeone or more fixed (i.e. placed at static physical locations within thefacility) tags 408, such as BLE tags or any other suitable short-rangecommunications component. Each tag 408 stores data, such as a URL,identifying the content server 132 (e.g. by the domain m.abc.ca) andalso identifying the location of the tag 408 itself. In other words, thetag 408 may store the URL “m.abc.ca/from=B7”. Upon placement in physicalproximity to the tag 408, the mobile device 150 retrieves theabove-noted URL, and may be redirected to the content server 132, whichmay then be configured to prompt the mobile device 150 for a destinationlocation, before generating a path and transmitting content as discussedabove in connection with block 245. As will now be apparent, the tags408 can be deployed throughout a facility that does not include a kiosk104.

In other embodiments, both the tag 408 and the kiosk 104 are deployed inthe facility. The tag 408 stores data (e.g. a URL) identifying therouting server 128 and the location of the tag 408 within the map. Themobile device 150 may interact with the kiosk 104 and routing server 128as discussed above to specify a destination location. Upon retrievingthe above-mentioned URL from the tag 408, the mobile device 150 istherefore configured to query the routing server 128 for the contentidentifier (which specifies the destination location as well as thelocation of the kiosk as a start location), replace the “from” location(originally the location of the kiosk 104) with the location from thetag 408, and query the content server 132.

The scope of the claims should not be limited by the embodiments setforth in the above examples, but should be given the broadestinterpretation consistent with the description as a whole.

1. A method of transmitting dynamic content to a mobile device,comprising: receiving, via an input device of a kiosk deployed in afacility, a command to present a portion of content associated with thekiosk; responsive to receiving the command, at the kiosk: controlling anoutput device of the kiosk to present the portion of the content; andtransmitting, to a routing server via a network, a preconfiguredidentifier of the kiosk and an identifier of the portion of the content,for subsequent retrieval by a mobile computing device.
 2. The method ofclaim 1, further comprising: subsequent to the transmitting, providingan identifier of he routing server to the mobile computing device. 3.The method of claim 2, wherein providing an identifier of the routingserver comprises generating a machine-readable indicium via the outputdevice, for capture by the mobile computing device.
 4. The method ofclaim 2, wherein providing an identifier of the routing server comprisestransmitting the identifier of the routing server to the mobilecomputing device via a short-range communications interface of thekiosk.
 5. The method of claim 1, further comprising: at the routingserver, receiving the preconfigured kiosk identifier and the contentportion identifier; and storing the content portion identifier inassociation with the kiosk identifier.
 6. The method of claim 5, furthercomprising: at the routing server, receiving a client request from themobile computing device containing the routing server identifier and thekiosk identifier; responsive to receiving the client request, retrievingthe content portion identifier corresponding to the kiosk identifier;and transmitting the content portion identifier to the mobile computingdevice, for retrieval of the content portion by the mobile computingdevice from a content server identified by the content portionidentifier.
 7. The method of claim 5, further comprising: at the routingserver, deleting the content portion identifier subsequent totransmitting the content portion identifier to the mobile computingdevice.
 8. A system for transmitting dynamic content o a mobilecomputing device, comprising: a routing server; a kiosk deployed in afacility, the kiosk associated with content and having an input deviceand an output device; the kiosk configured to: receive, via the inputdevice, a command to present a portion of the content; responsive toreceiving the command, control the output device to present the portionof the content; and transmit, to the routing server via a network, apreconfigured identifier of the kiosk and an identifier of the portionof the content, for subsequent retrieval by the mobile computing device.9. The system of claim 8, the kiosk further configured to: subsequent tothe transmitting, provide an identifier of the routing server to themobile computing device.
 10. The system of claim 9, the kiosk configuredto provide the identifier of the routing server by generating amachine-readable indicium via the output device, for capture by themobile computing device.
 11. The system of claim 9, the kiosk configuredto provide the identifier of the routing server by transmitting theidentifier of the routing server to the mobile computing device via ashort-range communications interface of the kiosk.
 12. The system ofclaim 8, the routing server configured to: receive the preconfiguredkiosk identifier and the content portion identifier; and store thecontent portion identifier in association with the kiosk identifier. 13.The system of claim 12, the routing server further configured to:receive a client request from the mobile computing device containing therouting server identifier and the kiosk identifier; responsive toreceiving the client request, retrieve the content portion identifiercorresponding to the kiosk identifier; and transmit the content portionidentifier to the mobile computing device, for retrieval of the contentportion by the mobile computing device from a content server identifiedby the content portion identifier.
 14. The system of claim 12, therouting server further configured to: delete the content portionidentifier subsequent to transmitting the content portion identifier tothe mobile computing device.